I have flashed my at&t tilt 2 with core cell evo v1.2 & it was working fine for awhile but now my screen is just black i can hear the phone make sounds and all but can't see the screen at all i really need help fixing this as this is the only phone i have any help or suggestions will be greatly appreciated thanks in advance.
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
heres a link to a potential problem solver. Try to stay away from CHT lock and auto update apps!
sagarc88 said:
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
Click to expand...
Click to collapse
yes i have done both and after the phone reboots i can hear sounds but i am still unable to see anything on the screen
Edit - I take that back, if it's still not working after a reboot
Have you tried entering the bootloader and re-flashing with the stock ROM?
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
steviewevie said:
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
Click to expand...
Click to collapse
i can't even tell if i can enter the bootloader screen because i can't see anything on the screen is there any way to tell if it's in the bootloader screen without being able to see the screen at all & if i do have a hardware problem (screen failure) how can i put stock spl & stock rom back on the phone to get it serviced
steviewevie said:
Edit - I take that back, if it's still not working after a reboot
Click to expand...
Click to collapse
if its still not working after a reboot then what? please help me i need a solution to fix this because if i can't even fix this how can i even send it in to get fixed i won't be able to because it has been flashed & has hardspl on it
"PLEASE HELP"
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
steviewevie said:
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
Click to expand...
Click to collapse
how can i flash anything if i can't see the screen?
Doo Doo said:
how can i flash anything if i can't see the scrren?
Click to expand...
Click to collapse
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
steviewevie said:
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
Click to expand...
Click to collapse
man i really need to fix this maybe you can ask around for me since i'm new here & really don't know anybody on this board
I know it's frustrating, I'd be kinda worried if I had an apparently-non-working screen too. But please be patient, and wait for more people to see your posting. The folks in the US will be coming online around this sort of time, so there will be more people looking in and hopefully someone can help further.
Flash without seeing the screen
Enter boot loader even if you can not see the screen. You can flash your phone to stock then enter boot loader again and hard spl. I had a similar situation and was able to complete the process and warranty repair with AT&T no problems, or you can pay to have it fixed at an outside shop. I was quoted 150 and refused to spend that muck so I flashed the phone without seeing the screen...
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Russ741 said:
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Click to expand...
Click to collapse
well when i plug my phone to the computer activesync is not popping up what can i do to get activesync to recognize my phone
can somebody please help me i need to reflash my phone but i am unable to see anything on my screen when i plug it up to my computer activesync is not working so what can i do please i really need help with this
Flashing witout screen
Step 1
Enter boot loader mode (* Remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, press the power button whilst holding down the Volume Down button.)
and attach to computer. (wait 30 to 60 seconds)
Step 2
Check device manager for HTC mobile sync under mobile devices.(Active sync will not work in boot loader mode)
Step 3
Flash using Rhodium CustomRUU on your PC. (use original ROM from At&T.
Step 4 repeat for Radio
Step 5 Use Stock_SPL_Restore_087.zip from http://forum.xda-developers.com/showthread.php?t=550131 repeat the process with it.
This should work it did for me. Let me know if you run into problems.
Related
Hello,
I've just installed HardSPL succesfully, after that I wanted to install MightyRom 4.6, so I did. That went succesfully too according to my computer. Now when i want to switch the phone on, it keeps hanging with the T-Mobile picture on it. I've done a hard reset for several times and also a few soft resets. I also took my battery out for a few minutes, but when I switch it on, the same thing happens.
Please help me out of this !
Ps. sorry for my bad english !
for taking a little stress from your brain take an other rom - orig. rom from your provider.....
(go bootloder from pda; if your orig. rom only one *.exe-file you have to extract (winzip/winrar) it before flashing; connect usb (bootloader screen change from serial to usb); than flash)
but before you do this, how long you have to wait and look to your screen?
it can be sometimes a very long time until a windows-screen is coming.
if your pda gets hot than dont wait and flash asap new rom.
after 5 minutes waiting without any changes you have to flash an other rom.
I think I may have the same problem with my Diamond. I also installed MightyRom 4.6. Now, when I power up my phone, I get through the RGB stage to a white backdrop with instructions in blue to push volume button up for a reboot to manufacturers settings or push volume button down to reboot to manufacturers settings and wipe the movinand....after I select either one, when it gets to the HTC logo (HTC Diamond in white on a black background), it freezes. My pc won't recognise my phone when I plug it in...
Do I now have a really gorgeous paperweight or can I hold my Diamond to my ear again? Insight into my problem would be much appreciated.
By the way, XDA Dev rocks. Thanks to all who made this site possible.
Brick or no brick ?
Oh, I forgot to mention that my phone was a non-branded HTC running a Duttys rom. I did not want to get a DOPOD Diamond from China Mobile as they cost more and I dunno if they put Big Brother software in there.
HateMan01 said:
I think I may have the same problem with my Diamond. I also installed MightyRom 4.6. Now, when I power up my phone, I get through the RGB stage and then when it gets to the HTC logo, it freezes. My pc won't recognise my phone when I plug it in...
Do I now have a really gorgeous paperweight or can I hold my Diamond to my ear again? Insight into my problem would be much appreciated.
By the way, XDA Dev rocks. Thanks to all who made this site possible.
Click to expand...
Click to collapse
hi try and do like okokur has posted
cobbs said:
hi try and do like okokur has posted
Click to expand...
Click to collapse
My pc won't recognise my phone when I plug it in...
HateMan01 said:
My pc won't recognise my phone when I plug it in...
Click to expand...
Click to collapse
do you have it in the boot loader before you plug it in to your pc?
Brickety brick, brick, brick...
My phone does not recognize my pc and vice versa. I tried plugging the phone in before booting it up. I tried while booting up. I tried at the white screen stage...nothing...help...
It also doesn't stay at the RGB screen for long...maybe 2 seconds...
Please break it to me gently if I have killed my HTC...I don't want to start drinking again...
...
My phone is a GSM Diamond. MightyRom 4.6 is for CDMA. If I combine the two(like I did) then am I screwed?
Can someone please give me some insight, please? I have been scouring the net for 3 days non stop now and my eyes are going to explode...
What is Jtag and can your average home user use it? Is it hardware or software...?
Cobbs: I assume when you say bootloader you mean something other than the RGB screen,,,cos as I stated in my first post, my phone does not stop on the RGB screen...
Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!
Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.
voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.
Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
delete. ......
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.
chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.
amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu
The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App
jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?
take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power
Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...
Hej,
Hopefully you all are fine and good in health...............
Now come to the point actually i had problem with my HTC Desie that was stuck up with its initial screen i mean when i turn on my phone it shows the htc logo then stuck up. Then i tried many times to hard reset but it could not work either, after that i download ROM "RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00 .32U_5.11.05.27_release_151783_signed.exe" and run from my pc (running windows 7) but after 65 % i got error during updating process and the utility shows how to recover it then according to the instructoins what i did is
1. Unplug my phone (dissconnect from pc)
2. Remove battery for 3 sec and plug it again.
3. Turn on the phone
4. Plug the USB (connect phone again)
but on the 3rd step when i plugged the battery it won't turn on neither charge or in short totally dead nothing happened to it .
I am requesting to all of you please please please suggest me what to do now, how can it work, how to turn it on again ............ is it bricked ??? if bricked then how to solve this problem ????.
Waiting for your responses......
Thanks in advance.
Be more specific.
- Can you still acces your recovery?
- If not, do you have a carrier specific rom? If so, download that rom, go into the bootloader, choose fastboot and run the rom. You can try this method also if you don't have a carrier specific rom.
Look here for a rom.
http://www.shipped-roms.com/index.php?category=android&model=Bravo
Lennyz1988 said:
Be more specific.
- Can you still acces your recovery?
- If not, do you have a carrier specific rom? If so, download that rom, go into the bootloader, choose fastboot and run the rom. You can try this method also if you don't have a carrier specific rom.
Look here for a rom.
http://www.shipped-roms.com/index.php?category=android&model=Bravo
Click to expand...
Click to collapse
no i don't have any access to recovery, because phone is not turn on how can i run this rom when phone is not connected or not power on........
by the way thanks for your suggestion.....
Hej,
After long discussion with HTC customer service and trying to convince them that the phone is not in water or in any wet place but they said that they found my phone or take my phone as liquid damage so my phone is out of warranty .
As they said that it has symptoms of liquid damage which turn white color of sticker into red/pink color. I even don't no how come but any how leave this.
Come to point, what can i do now my phone won't start i opened it disassemble then assemble everything but it won't power on even not charge ............
i am still stuck up with it even no idea what to do more
Need some suggestions can i order its flex cable or board or other stuff or what to do ??? how to power it on ???
Waiting for your response.
Thanks in advance.
arif01 said:
As they said that it has symptoms of liquid damage which turn white color of sticker into red/pink color. I even don't no how come but any how leave this.
Click to expand...
Click to collapse
Sorry, no idea for your original problem, but some small explanation where your so called water damage may come from. A friend of mine once had the same problem with a camera. The stickers can change color because of air-moisture. Especially if you carry the phone in your pocket and it is hot, your sweat leads to damp air in you pocket and affects those stickers.
I would try to argue with the htc support that it is not ok that keeping your cell phone in your pocket leads to a water damage. Perhaps they give in.
I wish you good luck with your phone.
mblaster
€: Here some link to back up my argumentation: http://www.wisegeek.com/what-is-a-water-damage-sticker.htm
You could try this...
arif01 said:
no i don't have any access to recovery, because phone is not turn on how can i run this rom when phone is not connected or not power on........
by the way thanks for your suggestion.....
Click to expand...
Click to collapse
You're problem sounds pretty similar to mine that I managed to solve. See my thread... http://forum.xda-developers.com/showthread.php?t=927702 (post #5).
Hope this helps.
Rich
babblerx said:
You're problem sounds pretty similar to mine that I managed to solve. See my thread... http://forum.xda-developers.com/showthread.php?t=927702 (post #5).
Hope this helps.
Rich
Click to expand...
Click to collapse
Thanks bro but the problem is my phone is not turn on , no power , no usb detection. Today i installed skd and used adb shell command but it says device not found what can i do more i dont understand
Please suggest me my friends.
Thanks in advance.
hey
i am trying the whole day to fix my phone. but i guess it is almost imposible :/
i can't get in recovery mode (nothing happens) and can't turn in on (only vibrates once, black screen)
i have been told to download to download
OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip
and rename it to PB99IMG.zip and put it on sd, which i did, but how can i flash it if my recovery mod can't start up?
please help?
ANY suggestions???? please heeelp! :/
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Click to expand...
Click to collapse
i installed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U _4.05.00.11_release_121684.exe
via fastbooth
do you know what to do... please say yes
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Click to expand...
Click to collapse
no i can't get into fast boot... ://
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.29....) exactly, but hopefully this gives you a clue where to look for a fix.
There were many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Richpopski123 said:
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
jcase??
i had this rom
http://forum.xda-developers.com/showthread.php?t=1040121
which didn't work and because of it i couldn't restore any of my previous roms. that is why i had to flash a rom from my computer fastbooth
have u any suggestions what should i do?
Tillus said:
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.21....) exactly, but hopefully this gives you a clue where to look for a fix.
There where many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Click to expand...
Click to collapse
yes... that makes sense. but does really no one have any clue what to do?? i worked the whole summer for this phone and now is gone
http://forum.xda-developers.com/showthread.php?t=748498
Probably the easiest and safest way ist to boot into fastboot although you don't see it and flash the newsest ruu,
so:
1) make sure, phone is off (i.e. pull battery and put back in)
2) push and hold "back" and hit power.
3) wait 30 seconds or so, to be on the safe side
4) connect phone to pc via usb
5) run RUU on PC, version 2.29.405... (RUU, not OTA!)
And make sure to have some juice in your battery
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Tillus said:
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Click to expand...
Click to collapse
how do i know that?
can u please stick with me... i will try to do that now
i apriciate your help... i think that nothink worse can be done to my phone, so i will try
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Tillus said:
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Click to expand...
Click to collapse
i hope its not branded
do i need to click od hold power button?
like you do, when you power on. The important part is to hold "back" while powering on
Tillus said:
like you do, when you power on. The important part is to hold "back" while powering on
Click to expand...
Click to collapse
do i have to hold down like 30 sec? no right?
i think this won't work
if i go to the sotre and give the device back... what would be a good excuse for phone not working?
jann32 said:
do i have to hold down like 30 sec? no right?
Click to expand...
Click to collapse
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all. Press and hold "back", press "power", release power, wait 3 seconds, release "back", wait 10 seconds and plug in usb, start ruu.
Thats all I wanted to say with my previous post. Sry, if it was confusing
Tillus said:
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all.
Click to expand...
Click to collapse
will try again
will the phone vibrate?
YES YES YES its upadatinjg.... hope this works
...my screen is back... but hopefully it finishes correctly... and doesn't go black again
what will happen if the phone is branded?
can i unbrand it?posebly not? cause its bricked ight? :/
no.
10charrrrr
If it is branded, you get a cid-error, so ruu wont finish. But your phone probably isn't branded, otherwise you would have come across problems during flashing custom roms or/or radios (-->goldcard). And because this doesn't seem to be the case, your device is not branded.
When the RUU is done, you phone is completely back to stock and you can do whatever you like to it...
Tillus said:
no.
10charrrrr
Click to expand...
Click to collapse
my phone works!!
i can not tell u how greatfull i am
THANK U
thank u for sticking with me again
Hey all,
I have a HTC Desire (PB99200) which won't switch on, recognise a charger/ connection to a PC or enter recovery etc. This was failed update, think I used the wrong RRU as I didn't know about the different versions SLCD/AMOLED.
So as far as I know the device is dead in the water, what I want to know is can it be salvaged?
I'm basically a noob but any help would be greatful
bortak's troubleshooting guide stickied to the top of Q&A, point [5]
If that RUU doesn't work, I recommend find and flash the 2.3.3 GB RUU from shipped ROMs
Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible
robbiejuk08 said:
Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible
Click to expand...
Click to collapse
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)
jmcclue said:
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)
Click to expand...
Click to collapse
Did this and still nothing, even the RRU software can't see it
robbiejuk08 said:
Did this and still nothing, even the RRU software can't see it
Click to expand...
Click to collapse
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.
jmcclue said:
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.
Click to expand...
Click to collapse
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway
robbiejuk08 said:
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway
Click to expand...
Click to collapse
Sorry I read your post too quickly
So nothing comes up on screen at all when you try to get to bootloader?
I'm trying to remember whether bootloader is actually 'there', but just not visible if you flashed an SLCD RUU on an AMOLED desire or vice versa.
If it's actually there, then it may be possible to flash the RUU via PB99IMG.zip method, not tried it this way blind but worth a shot before you take it for repair.
- Try the 2.3.3 RUU from here (thanks to @jmcclue)
- Put the zip as it is on the root of the sdcard (not inside any folder), then attempt to boot to bootloader (vol down + power)
- Wait at least 30 seconds - 1 minute for it to scan and load the file, then press volume up to accept the RUU.
- Wait for it to flash, pray that it works!
Also have a look here, you're following this procedure without the screen basically.
Reread my original post in full
robbiejuk08 said:
Reread my original post in full
Click to expand...
Click to collapse
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!
eddiehk6 said:
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!
Click to expand...
Click to collapse
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.
robbiejuk08 said:
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.
Click to expand...
Click to collapse
So if it was working fine before, I doubt the RUU has broken the charging capability.
The only way I guess is to try the PB99IMG.zip watching the video at the same time plus waiting a few seconds longer just in case. Think you have to press volume up or power at the end to reboot can't remember, or battery pull and hope it turns on afterwards.
No guarantee it will work, though I've seen many people in these forums recover 'black screen after ruu' issue. Still worth exhausting this method before repair